Radio access network based traffic steering to non-cellular access

ABSTRACT

Various communication systems may benefit from traffic steering. For example, radio access network based traffic steering can be used to benefit of communications by steering traffic to Wi-Fi leveraging Hotspot 2.0. A method can include determining that an off-load condition exists in an area of a radio access network. The method can also include commanding a user equipment to off-load to non-cellular radio access based on the determining.

BACKGROUND Field

Various communication systems may benefit from traffic steering. For example, radio access network based traffic steering can be used to benefit communications by steering traffic to Wi-Fi leveraging Hotspot 2.0.

Description of the Related Art

Non-cellular radio access technologies, such as Wi-Fi networks, are becoming an integral part of mobile broadband. Wi-Fi is already standard feature on smart phones, tablets and laptops and is used by many network operators. However, despite the popularity of Wi-Fi, operators lack a measure of control and lack dynamic mechanisms for determining user device movement between mobile and Wi-Fi networks.

Conventional network selection tools guiding how the user device moves between mobile and Wi-Fi networks are static in nature. For example, third generation partnership project (3GPP) release 8 (rel-8) technical specification (TS) 23.402 Access Network Discovery and Selection Function (ANDSF), which is hereby incorporated herein by reference in its entirety, does not support online communication between user device and ANDSF server to dynamically set network selection policies to user device based on changing network environment.

3GPP TS 23.402 allows defining static Wi-Fi selection rules into user devices but as such does not support online on need-based communication. ANDSF allows defining detailed criteria for network selection, like time of day, location and application.

A 3GPP standard, for example 3GPP rel-8 TS 23.401, which is hereby incorporated herein by reference in its entirety, defines Radio Access Technology (RAT) Frequency Selection Priority (RFSP) allowing a mobile operator to control subscriber 2G/3G/LTE access network selection in idle mode and operator resource assignments from these networks for the user in active mode. For one user 1: 3G 2100 MHz 2: 4G 2600 MHz 3: 2G 900 MHz may be applied and to another user 1: LTE 2600 MHz 2: LTE 800 MHz 3: 3G 2100 MHz 4: 2G 900 MHz may be applied.

SUMMARY

According to a first embodiment, a method may include determining that an off-load condition exists in an area of a cellular radio access network. The method may also include commanding a user equipment to off-load to non-cellular radio access based on the determining.

According to a second embodiment, a method may include receiving a message commanding off-load to non-cellular access. The method may also include searching for non-cellular access points based on the received message. The method may further include identifying at least one non-cellular access point based on the searching.

According to a third embodiment, a method may include determining whether a user equipment is to be permitted a non-cellular access. The method may also include instructing a non-cellular access network based on the determination.

According to a fourth embodiment, a method may include receiving instruction regarding whether a user equipment is to be permitted non-cellular access. The method may also include receiving a request from a user equipment regarding a property of a non-cellular access. The method may further include responding to the request based on the instruction regarding whether the user equipment is to be permitted non-cellular access.

According to a fifth embodiment, an apparatus can include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to determine that an off-load condition exists in an area of a cellular radio access network. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus at least to command a user equipment to off-load to non-cellular radio access based on the determining.

According to a sixth embodiment, an apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to receive a message commanding off-load to non-cellular access. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus at least to search for non-cellular access points based on the received message. The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus at least to identify at least one non-cellular access point based on the searching.

According to a seventh embodiment, an apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to determine whether a user equipment is to be permitted a non-cellular access. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus at least to instruct a non-cellular access network based on the determination.

According to an eighth embodiment, an apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to receive instruction regarding whether a user equipment is to be permitted non-cellular access. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus at least to receive a request from a user equipment regarding a property of a non-cellular access. The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus at least to respond to the request based on the instruction regarding whether the user equipment is to be permitted non-cellular access.

According to a ninth embodiment, an apparatus may include determining means for determining that an off-load condition exists in an area of a cellular radio access network. The apparatus may also include commanding means for commanding a user equipment to off-load to non-cellular radio access based on the determining.

According to a tenth embodiment, an apparatus may include receiving means for receiving a message commanding off-load to non-cellular access. The apparatus may also include searching means for searching for non-cellular access points based on the received message. The apparatus may further include identifying means for identifying at least one non-cellular access point based on the searching.

According to an eleventh embodiment, an apparatus may include determining means for determining whether a user equipment is to be permitted a non-cellular access. The apparatus may also include instructing means for instructing a non-cellular access network based on the determination.

According to a twelfth embodiment, an apparatus may include receiving means for receiving instruction regarding whether a user equipment is to be permitted non-cellular access and for receiving a request from a user equipment regarding a property of a non-cellular access. The apparatus may further include responding means for responding to the request based on the instruction regarding whether the user equipment is to be permitted non-cellular access.

According to thirteenth through sixteenth embodiments, respectively, a non-transitory computer-readable medium can be encoded with instructions that, when executed in hardware, perform a process. The process can correspond to the method of the first through fourth embodiments, respectively.

BRIEF DESCRIPTION OF THE DRAWINGS

For proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

FIG. 1 illustrates a method according to certain embodiments.

FIG. 2 illustrates another method according to certain embodiments.

FIG. 3 illustrates a further method according to certain embodiments.

FIG. 4 illustrates an example information element according to certain embodiments.

FIG. 5 illustrates another method according to certain embodiments.

FIG. 6 illustrates a method according to certain embodiments.

FIG. 7 illustrates messaging according to certain embodiments.

FIG. 8 illustrates an additional method according to certain embodiments.

FIG. 9 illustrates a system according to certain embodiments of the invention.

DETAILED DESCRIPTION

Certain embodiments may provide operators with tools to perform various functions. For example, certain embodiments may help operators balance traffic between mobile and Wi-Fi networks to improve user experience and avoid congestion on one of the networks. Moreover, certain embodiments may help to perform 3G/LTE cell congestion based offload to Wi-Fi to improve user experience and use Wi-Fi as a backup capacity when needed. Furthermore, for example, certain embodiments may permit offloading UE to roaming partner Wi-Fi costing extra for the operator only when own network, mobile and optionally own Wi-Fi hotspots, does not have enough available capacity, like during a mass event. Likewise, certain embodiments may permit operators to keep a user in 3G/LTE for ensured service quality or similar purposes and to offload to Wi-Fi only when cell becomes congested

Conventionally, user equipment and devices including smartphones prioritize Wi-Fi over mobile networks. Thus, for example, when a user uses an application, like browser or a streaming video service, the device goes automatically to pre-configured/earlier used Wi-Fi, when available, taking data away from mobile network. According to certain embodiments, mobile operator tools can be used to balance traffic between mobile and Wi-Fi.

Hotspot 2.0 is a standard for local area non-cellular wireless communication that may be supported by new Wi-Fi devices and networks. Moreover, Hotspot 2.0 includes Access Network Query Protocol (ANQP) which the UE is able to use to acquire additional Wi-Fi access point (AP) information before connecting to the hotspot. For example the UE can learn the load of the Wi-Fi AP to avoid connecting to a congested AP, services provided through the hotspot, like whether there is an association to home operator, AP capabilities, list of operator friendly names, public land mobile network (PLMN) identifier reachable through the Wi-Fi network, performance data (like AP load, WAN (Wide Area Network) metrics including e.g. uplink/downlink speed and load), etc. Herein, access points running Hotspot 2.0 as well as other WiFi access points are examples of “non-cellular” access.

FIG. 1 illustrates a method according to certain embodiments. As shown in FIG. 1, at 110, a radio access network (RAN) can command a user equipment (UE) or other user device to look for (or not to look for) suitable non-cellular access, such as Wi-Fi APs. This may be triggered by a prior determination in the RAN at 105 that there is cell congestion or a lack of cell congestion. RAN can utilize system information block (SIB) message(s), radio resource control (RRC) message(s), cell broadcast, paging or any other suitable communication means to communicate this command to the user equipment (UE). In case the method is based on UE-specific signaling, the UE can, at 115, indicate to the RAN whether it supports Wi-Fi and is enabled, and information if he UE has already checked the availability of Wi-Fi. Optionally, the UE can indicates to RAN only the Wi-Fi networks the UE can access, for example the Wi-Fi networks for which the UE has authentication credentials. This may allow RAN to know if UE has Wi-Fi available and the UE can access the Wi-Fi. The UE may also indicate current load information and available signal quality characteristics of the networks that the UE can access and/or for which the UE has authentication credentials.

The RAN can, more precisely, control when and where UE uses 3GPP and Wi-Fi networks. For example, when the UE has been commanded to look for Wi-Fi network, at 110, the UE and Wi-Fi AP Hotspot 2.0 capabilities enable the UE to find a suitable hotspot, at 120. The RAN can also, at 130, control when the UE needs to return back to the mobile network. Alternatively, this information can also be conveyed via the Wi-Fi network. Optionally, the RAN can control, at 140, when the UE cannot access Wi-Fi hotspot. As a result, a simple solution for dynamic RAN-controlled Wi-Fi selection can be created supported by UEs and networks.

FIG. 2 illustrates a method of user equipment configuration and querying. As shown in FIG. 2, at 210, a device management (DM) server can configure Hotspot 2.0 policies into UEs, for example operator subscriber devices having Wi-Fi service. Based on over the air configured policies, at 220, the UE can identify online by making an ANQP query to a hotspot if the hotspot supports UE services and has, for example, a relationship with a UE home operator.

Over the air configuration of Hotspot 2.0 policies is one approach. Without over the air configuring Hotspot 2.0 policies to the UE, the user may need to manually configure network selection preferences into the UE or an operator needs to pre-install Hotspot 2.0network selection preferences to the UE for example before selling the UE to the subscriber.

However, Hotspot 2.0 may support automatic Wi-Fi network selection for limited use scenarios. For example, if a UE can see any AP advertising connection to UE's home mobile/Wi-Fi operator, UE can automatically connect to that without any Hotspot 2.0 policy information. But Hotspot 2.0 may not provide any way to differentiate between different Wi-Fi networks. If a UE can see two different service set identifiers (SSIDs)/Wi-Fi networks both advertising connection to UE's home (Wi-Fi) operator, it may be up to the UE's implementation/user to select the Wi-Fi AP/network. An exception to this approach is a Wi-Fi network where both Wi-Fi radio access network and service provider are operated by the same operator that is also UE's home (Wi-Fi) operator: If a UE can see an AP/Wi-Fi network that advertises being operated by UE's home (Wi-Fi) operator and one of the service providers is also UE's home (Wi-Fi) operator, UE can select that Wi-Fi network before any other Wi-Fi network.

FIG. 3 illustrates a method according to certain embodiments. RAN can be eNode B (eNB), radio network controller (RNC) or base station controller (BSC) in current networks containing Radio Resource Management (RRM) and Radio Access Technology (RAT) coordination. RAN can be also a centralized RRM element or centralized RRM functionality in an existing element, like RNC. The RAN can control UE mobile network (for example, 2G, 3G, LTE, or LTE-A) and Wi-Fi network usage. For example, by default operator business strategy is used where, for example, a voice-centric user is kept in 2G network by default and data-centric subscribers in 3G/LTE networks by default, and Wi-Fi network can be used only as capacity backup network for data users. For example, UEs may use mobile network by default and Wi-Fi only when commanded by RAN.

RAN RRM, scheduler, admission control etc. can, at 310, determine network congestion, inability to maintain quality of service (QoS) or quality of experience (QoE) for a user, a user experience problem, a situation in which the UE has poor radio quality due to being located at cell edge or far from a base station, or the like condition. When such a determination is affirmative, the RAN can, at 320, select UEs to be offloaded to a nearby Wi-Fi network. The selected UE can be for example platinum, gold, silver or bronze UE, UE on cell edge having challenging radio conditions, UE having selected ongoing service (like P2P or streaming video services), UE having defined QoS profile/characteristics, UE having poor radio condition, or the like.

After selecting one or more UE(s), the RAN, at 330, can signal a command for the UE(s) to switch to Wi-Fi network. The command can be signaled in a variety of ways. For example, the command can be signaled in RRC or in another bearer/mobility management message as a new field or as an extension to an existing field. For example, the extension may be an extension to current handover command where Wi-Fi network is indicated.

In order to prevent RAN from continuously commanding the UE to go to Wi-Fi when it is not possible for the UE, the UE can indicate to the network whether it supports Wi-Fi and whether Wi-Fi is enabled (optionally if the UE has authentication credentials to available Wi-Fi networks), if, for example, the UE has already checked Wi-Fi availability with the result “no Wi-Fi available.” This information can be realized with a new field or as an extension to an existing field. Only when the UE indicates Wi-Fi is enabled and no indication about “no Wi-Fi available,” the RAN can send the command to the UE to try to go to Wi-Fi. Alternatively RAN could also allocate requested resource from 3GPP network but at the same time could indicate to the UE that WLAN is a preferred method. UE could then search for WLAN and if found then could request further resources from the WLAN.

The command can alternatively be signaled in SIB or RRCConnectionRelease message by defining Wi-Fi or Hotspot 2.0 ANQP as a new RAT priority in addition to GSM 1800, 3G 2100 etc. RATs. See in below an example about RFSP mechanism details.

In another alternative, the command can be signaled in an SIB message in case the command is generic for all UEs camped into the cell. Alternatively, the command can be signaled in another suitable 3GPP message transferred between UE and RAN over the radio.

If a RAN decides to move a UE to a specific Wi-Fi network, which may be identified for example with SSID and MAC, the RAN may send user or UE profile/characteristics to the target Wi-Fi network or Wi-Fi AP in a separate message. The profile/characteristics may include one or more of the following: Full or subset of 3GPP QoS profile, Wi-Fi Multimedia (WMM) QoS profile (for example, RAN can convert 3GPP QoS into WMM QoS), user/UE identities (such as IMSI and/or MAC), services the UE had active under RAN, and the like. This may enable the Wi-Fi network to appropriately handle the UE from the point the UE accesses the Wi-Fi. For example, the Wi-Fi AP may be able to prioritize UE and/or traffic, reserve enough resources for the UE in admission/resource control, and so on. The message the RAN sends to Wi-Fi can be the same or different from a message the RAN may use to control whether the UE is allowed to access the Wi-Fi or not.

Other characteristics or properties can also be communicated. For example, in addition to the characteristics listed above, the RAN can provide the Wi-Fi network/controller with traffic filters enabling the Wi-Fi network (for example, Wi-Fi GW) later to route selected flows to packet core and PGW and route other traffic of a single user directly to the Internet. The traffic filters can be based on for example 3GPP Traffic Flow Templates used with PDP Contexts/Sessions or ANDSF ISRP (Inter-System Routing Policies). In case ANDSF ISRP are used, ANDSF server may deliver UE specific ISRP policies (defining application/service specific network selection policies) also to RAN and/or Wi-Fi GW in addition to delivering the policies to the UE.

It is not necessary for the RAN to know/identify MAC of the target network. In an alternative, however. RAN may identify Homogenous Extended Service Set ID (HESSID), or other network identification information available e.g. through Hotspot 2.0, though.

When the RAN communicates with the Wi-Fi network, this can be communication with a Wi-Fi controller or similar. It is not necessary for the RAN to communicate directly to any WLAN AP, although direct communication could be used if the APs are autonomous.

Thus, in certain embodiments the RAN may first determine under which Wi-Fi controller the device exists. A device may, therefore, in certain cases monitor and report specific Wi-Fi AP by MAC address or Wi-Fi network by HESSID. Thus, in certain cases the Wi-Fi AP may be identified in a non-unique way to the RAN, such as by the network to which the Wi-Fi AP is associated.

The RAN could deliver WMM QoS profile to a Wi-Fi controller. This may allow WLAN to prioritize downlink traffic for such a user. Typically in WMM enabled networks each WMM class creates own queue, both in uplink and in downlink. In uplink the random access parameters for high priority WMM class allow more opportunities to send than for lower priority VMM class. In downlink the AP can freely decide whose packet will be scheduled first. Conventionally, the highest priority WMM queue is always drained before lower priority queues, although in certain embodiments this could be modified.

If channel reservation (WMM-AC) is deployed, then APs may be able to reserve capacity, for example fixed slots, for devices to use.

RAN can identify the target Wi-Fi AP by, for example, commanding the UE to perform Wi-Fi measurements (on all available Wi-Fi APs or selected Wi-Fi APs communicated to the UE) where the UE includes for example SSID, radio quality and MAC of detected Wi-Fi AP into the measurement report sent to the RAN.

FIG. 4 illustrates an example information element according to certain embodiments. The example information element shown in FIG. 4 can be introduced into SIB, RRC etc. message transferred between RAN and UE. The fields shown are only exemplary, and not all the fields need to be present. The example information element defines optional info giving additional criteria for the UE to consider when selecting Wi-Fi network to be used, based on information Hotspot 2.0 supports.

One alternative when using RFSP mechanism is to include Hotspot 2.0/ANQP as one RAT priority or define Wi-Fi in general as one RAT priority leading the UE to consider Hotspot 2.0 info. In the discussion below, the RFSP RAT priority table is internal to RAN, where the RAN selects an RFSP index to be used for a certain UE or for all UEs in the cell. The RAN can then communicate the RAT priorities, not RFSP index, to affected UEs. For example, in the discussion below the RFSP index is used for the UE and thus the UE can receive HS2.0 ANQP as the highest RAT priority indicating to the UE to utilize Wi-Fi network before utilizing LTE network. In case RAN used RFSP index 2 for the UE, the UE would consider only 3GPP networks when selecting RAT/network to be used. An exception may be home, enterprise etc., where the Wi-Fi network that user may have configured into the UE and that the user wants to use when available may be permitted. By contrast, certain embodiments relate to controlling Wi-Fi network use of operator own hotspots or hotspot providers having roaming agreement to home operator but not limited to those.

TABLE 1 RFSP policy table for a user instructing initially to utilize only mobile networks. RFSP Priority Index 7 6 5 4 3 2 1 0 1 HS2.0 LTE2.6 UMTS2.1 UMTS1900 2G1800 2G900 ANQP 2 LTE2.6 UMTS2.1 UMTS1900 2G1800 2G900 . . . . . . . . . 256 

FIG. 5 illustrates another method according to certain embodiments. As an alternative, without defining a new explicit command to instruct UE to go to a Wi-Fi, a new SIB element can be defined to address certain number of different user groups. For example, a two-byte field can be introduced, where for example 12 first bits represent 12 different user classes and four bits are reserved for other/future use. The length of this field can also be something else than two bytes. Each subscriber can be allocated to one or more of these user classes.

As shown in FIG. 5, at 510 this allocation information can be stored as part of the subscription profile in home location register (HLR)/home subscriber server (HSS), policy control server such as a policy charging and rules function (PCRF), or like network component storing user profile details. Whenever a bit corresponding to one user class is set to ‘1’, UEs belonging to that user class can, at 520, actively try to connect to the Wi-Fi, using Hotspot 2.0 (HS2.0) or any other available mechanisms. When the bit is set back to zero, or when UE moves into a new cell with the bit set to zero, at 530 the UEs belonging to that user class can stop using Wi-Fi and can start to prefer a 3GPP RAT.

FIG. 6 illustrates a method according to certain embodiments. At 610, a UE can receive a message from a RAN to utilize Wi-Fi network. Therefore, at 620, the UE can start scanning or otherwise searching for Wi-Fi radio and see which Wi-Fi networks are available. Once the UE finds a Wi-Fi network at 630, the UE can use Hotspot 2.0 ANQP at 640 to query, from the Wi-Fi network, for the properties, for example the characteristics, of the network. Without ANQP, the UE can attempt to connect to the Wi-Fi network or learn Wi-Fi characteristics through other IEEE defined mechanisms (like 802.21 Media Independent Handover mechanisms). However, in this case the Wi-Fi performance may not be known before connecting to the AP, unless other 802.11 mechanisms make this available to the UE. In case service providers, roaming consortiums, load/performance etc. meet the UE requirements and optionally RAN set requirements, the UE may select the Wi-Fi AP (hotspot). In case the UE is unable to find a suitable hotspot, at 650 the UE stays or comes back into the mobile network. Here, querying for the properties of the non-cellular access network is one example of requesting properties of the non-cellular access network.

FIG. 7 illustrates messaging according to certain embodiments. More particularly, FIG. 7 illustrates Hotspot 2.0 ANQP messaging (ANQP over GAS) as part of associating and authenticating to a hotspot.

As shown in FIG. 7, the UE can receive a beacon from a Wi-Fi hotspot, and send a generic advertisement service (GAS) initial request to the hotspot. In reply, the Wi-Fi hotspot can provide a GAS initial response. This can occur prior to authentication or association.

As mentioned above in reference to FIG. 1, when a RAN has commanded a UE to utilize Wi-Fi network, the RAN may be able to bring the UE back to the mobile network when needed, for example when cell congestion situation is over. The RAN can utilize various mechanisms for doing that.

For example, the RAN can use paging. The UE using the Wi-Fi network can still monitor a paging channel in order not to miss an incoming call or message. Thus, the RAN can send a paging request message with the UE id, for example a temporary ID or international mobile subscriber identity (IMSI) or the like, telling the UE, for example, in a new paging reason code “return back to 3GPP.” The UE detecting such a page can return to a 3GPP network and stop using a Wi-Fi network. Optionally the UE can perform access to the 3GPP cell enabling RAN to know the UE has stopped using Wi-Fi.

Alternative, the RAN can use an RFSP mechanism. If an RFSP mechanism is used to steer the UE to Wi-Fi, a T320 timer already defined into RFSP can be used to indicate a validity period for the new RAT priorities. After T320 expires, the UE can revert to earlier used RAT priorities and can come back to a 3GPP network. RAN may set a value for the T320, for example based on pre-configuration, like 15 minutes, or additional intelligence may be used, like history data or user subscription/profile details (for example, a gold user may have a shorter/longer timer than a bronze user), to define the validity period for Wi-Fi selection rule.

In another alternative, the RAN can use a Hotspot 2.0/Wi-Fi mechanism. When the RAN decides a UE should come back from the Wi-Fi network to the 3GPP network, for example when a congestion situation is over, the RAN may send a message to the Wi-Fi network serving the UE to instruct the UE to return to 3GPP network. For example, any of the following three mechanisms may be used.

According to a first option, IEEE 802.11 or Hotspot 2.0 can add a new message or new information element to an existing message that can be sent to a UE utilizing the Wi-Fi network. The UE receiving this information can return back to a 3GPP network and can update RAT priorities. As an example, Hotspot 2.0 can define a triggering mechanism for a UE to contact policy server after successful extensible authentication protocol (EAP) authentication. This trigger can be indicated to the UE using 802.11 Wireless Network Management (WNM) notification mechanism. This mechanism can be extended for 3GPP—Wi-Fi interworking by, for example, defining a new sub-element that indicates to the UE to prefer 3GPP RAT instead of Wi-Fi.

According to a second option, a new EAP-SIM/AKA/AKA′ parameter can be added into EAP signaling indicating that the Wi-Fi network does not accept the UE to continue Wi-Fi usage. With the new parameter, it is possible to define UE behavior in 3GPP for Wi-Fi-enabled 3GPP devices.

According to a third option, Wi-Fi network admission control, such as a AAA server, can deny Wi-Fi access for the UE upon RAN or 3GPP network request. For example, a similar procedure can be used as is used when the UE has used Wi-Fi quota or time, for example when a user has bought two hour Wi-Fi access in an airport and it expires. This procedure can deny further Wi-Fi service to the UE, causing the UE to come back to 3GPP network to continue using services. However, without definition of additional functionality, UEs' behavior after receiving this kind of information may be implementation-specific. As an example, a UE may blacklist a Wi-Fi network denying access from the UE and may avoid connecting to the Wi-Fi network indefinitely or for a long time.

In a further alternative, the RAN can use an SIB mechanism. For example, the RAN may indicate in SIB message(s) to the UE that the UE is commanded to return back to 3GPP network. The UE may monitor SIB messages even while using Wi-Fi. There are several options for such a mechanism. For example, according to a first option the RAN can include a list of UE IDs, like temporary ID, into a specific SIB message. According to a second option, the RAN can enable a bit in a selected SIB message telling the UEs in a cell either to revert back to earlier used RAT priorities or instructing the UEs to acquire new RAT selection policies from the RAN, where new RFSP RAT priorities can be sent to the UE using SIB and/or RRC message. According to a third option, a RAN can instruct UEs belonging to a certain user class to come back to cellular network by setting the corresponding bit from one to zero for that user class in the new SIB element, similar to the approach described above.

In order for a RAN/3GPP network/operator to be sure that a user uses 3GPP by default and Wi-Fi only when decided by the 3GPP network, the following options can be used at least for operator own hotspots and optionally for selected roaming partner networks.

FIG. 8 illustrates a method according to certain embodiments. As shown in FIG. 8, at 810 the RAN can instruct the Wi-Fi network to provide information to a UE that performs a Hotspot 2.0 ANQP query or uses other 802.11 messaging to learn Wi-Fi AP characteristics. This may lead to the UE not selecting the Wi-Fi AP. For example, at 820 the RAN can send UE_WIFI_PERMISSION (UE ID, disabled) message to ANQP server when UE connects to a new cell. If UE makes ANQP query to Wi-Fi network, the ANQP server can learn, at 830, at least UE medium access control (MAC) address from Wi-Fi AP that can be mapped, at 840, to UE ID using mapping table unless UE ID equals MAC address. When UE with “disabled” status makes an ANQP query, at 850 the ANQP server can indicate “load=FULL” or equal information into ANQP response message to indicate to the UE “don't connect to me.” If there is, for example, cell congestion and the UE needs to be offloaded to Wi-Fi, the RAN can send UE_WIFI_PERMISSION (UE ID, enabled) message to ANQP server causing the ANQP server, at 860, to send “normal” ANQP information to the UE, thereby allowing the UE to select the Wi-Fi AP.

Alternatively, Wi-Fi network access/admission control, like a AAA server, can deny Wi-Fi access for the UE upon RAN or 3GPP network request, potentially with a new EAP-SIM/AKA/AKA′ parameter as described above for Hotspot 2.0/Wi-Fi mechanisms. For example, upon cell congestion, the RAN can enable Wi-Fi access/service for the UE and thus the UE can access the Wi-Fi network.

FIG. 9 illustrates a system according to certain embodiments of the invention. It should be understood that each block of the flowchart of FIG. 1-3 or 5-8 and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry. In one embodiment, a system may comprise several devices, such as, for example, network element 910 and user equipment (UE) or user device 920. The system may comprise more than one UE 920 and more than one network element 910, although only one of each is shown for the purposes of illustration. A network element can be an access point, a base station, an eNode B (eNB), server, host or any of the other network elements discussed herein. Each of these devices may comprise at least one processor or control unit or module, respectively indicated as 914 and 924. At least one memory may be provided in each device, and indicated as 915 and 925, respectively. The memory may comprise computer program instructions or computer code contained therein. One or more transceiver 916 and 926 may be provided, and each device may also comprise an antenna, respectively illustrated as 917 and 927. Although only one antenna each is shown, many antennas and multiple antenna elements may be provided to each of the devices. Other configurations of these devices, for example, may be provided. For example, network element 910 and UE 920 may be additionally configured for wired communication, in addition to wireless communication, and in such a case antennas 917 and 927 may illustrate any form of communication hardware, without being limited to merely an antenna. Likewise, some network elements 910 may be solely configured for wired communication, and such cases antenna 917 may illustrate any form of wired communication hardware, such as a network interface card.

Transceivers 916 and 926 may each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception. The transmitter and/or receiver may also be implemented as a remote radio head which is not located in the device itself, but in a mast, for example. It should also be appreciated that according to a liquid or flexible radio concept, the operations and functionalities may be performed in different entities, such as nodes, hosts or servers, in a flexible manner. In other words, division of labor may vary case by case. One possible use is to make a network element to deliver local content. One or more functionalities may also be implemented as a virtual application that is as software that can run on a server.

A user device or user equipment may be a mobile station (MS) such as a mobile phone or smart phone or multimedia device, a computer, such as a tablet, provided with wireless communication capabilities, personal data or digital assistant (PDA) provided with wireless communication capabilities, portable media player, digital camera, pocket video camera, navigation unit provided with wireless communication capabilities or any combinations thereof.

In an exemplary embodiment, an apparatus, such as a node or user device, may comprise means for carrying out embodiments described above in relation to FIG. 1-3 or 5-8. In an exemplary embodiment, an apparatus, such as a user device, may comprise means (924) for identifying at least one non-cellular access point based on searching. Another exemplary apparatus, such as a node, may comprise means (914) for determining that an off-load condition exists in an area of a radio access network.

Processors 914 and 924 may be embodied by any computational or data processing device, such as a central processing unit (CPU), digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), digitally enhanced circuits, or comparable device or a combination thereof. The processors may be implemented as a single controller, or a plurality of controllers or processors.

For firmware or software, the implementation may comprise modules or unit of at least one chip set, for example, procedures, functions, and so on. Memories 915 and 925 may independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate therefrom. Furthermore, the computer program instructions may be stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language. The memory or data storage entity may be internal but may also be external or a combination thereof, such as in the case when additional memory capacity is obtained from a service provider. The memory may be fixed or removable.

The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as network element 910 and/or UE 920, to perform any of the processes described above (see, for example, FIGS. 1-3 and 5-8). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions or one or more computer program (such as added or updated software routine, applet or macro) that, when executed in hardware, may perform a process such as one of the processes described herein. Computer programs may be coded by a programming language, which may be a high-level programming language, such as objective-C, C, C++, C#, Java, or the like, or a low-level programming language, such as a machine language, or assembler. Alternatively, certain embodiments of the invention may be performed entirely in hardware.

Furthermore, although FIG. 9 illustrates a system including a network element 910 and a UE 920, embodiments of the invention may be applicable to other configurations, and configurations involving additional elements, as illustrated and discussed herein. For example, multiple user equipment devices and multiple network elements may be present, or other nodes providing similar functionality, such as nodes that combine the functionality of a user equipment and an access point, such as a relay node.

One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.

Glossary

2G Second Generation

3G Third Generation

3GPP Third Generation Partnership Project

ANDSF Access Network Discovery and Selection Function

ANQP Access Network Query Protocol

AP Access Point

BSC Base Station Controller

DM Device Management

eNB eNode B

GAS Generic Advertisement Service

HESSID Homogenous Extended Service Set ID

HetNet Heterogeneous Networks (here 3GPP and Wi-Fi focus, WiMAX not excluded)

HLR Home Location Register

HSS Home Subscriber Server

IMSI International Mobile Subscriber Identity

LTE Long Term Evolution

MAC Medium Access Control

MS Mobile Station

PDA Personal Data or Digital Assistant

RAN Radio Access Network

RAT Radio Access Technology

RFSP Radio Frequency Selection Priority (RAT/Frequency Selection Priority)

QoE Quality of Experience

QoS Quality of Service

RNC Radio Network Controller

RRC Radio Resource Control

RRM Radio Resource Management

SIB System Information Block

SSID Service Set Identifier

TS Technical Specification

UE User Equipment

WNM Wireless Network Management 

We claim:
 1. A method of a cellular radio access network steering network traffic, comprising: determining that an off-load condition no longer exists in an area of the cellular radio access network that a user equipment is located in; and sending instruction, via a non-cellular network, to the user equipment to return to the cellular radio access network.
 2. The method of claim 1, further comprising: notifying the user equipment to contact a policy server after successful extensible authentication protocol authentication.
 3. The method of claim 1, further comprising: sending an indication to the user equipment of an availability of cellular radio access on the cellular radio access network.
 4. The method of claim 1, wherein the off-load condition comprises a cell network congestion state or a quality of service of the cellular radio access network.
 5. The method of claim 1, further comprising: sending instruction to the user equipment that the non-cellular network is preferred such that the user equipment prioritizes offloading to the non-cellular network while on the cellular radio access network.
 6. The method of claim 1, further comprising: sending instruction to the user equipment that the cellular radio access network is preferred such that the user equipment prioritizes returning to the cellular radio access network while on the non-cellular network.
 7. The method of claim 1, further comprising: preventing the user equipment from returning to the cellular radio access network prior to instructing the user equipment to return to the cellular radio access network.
 8. The method of claim 1, further comprising: selecting the user equipment to return to the cellular radio access network from a plurality of user equipment within the area of the cellular radio access network.
 9. The method of claim 1, wherein the non-cellular network is a Wi-Fi network.
 10. The method of claim 1, sending instructions to the user equipment to offload to the non-cellular network via an 802.11 or Hotspot 2.0 mechanism.
 11. A system for steering network traffic, comprising: a cellular radio access network; and a user equipment having access to a non-cellular radio access network; wherein the cellular radio access network is configured to determine that an off-load condition no longer exists in an area of the cellular radio access network that the user equipment is located in; and wherein the cellular radio access network is configured to return the user equipment to the cellular radio access network from the non-cellular radio access network in response to determining that the off-load condition no longer exists.
 12. The system of claim 11, wherein the cellular radio access network is configured to notify the user equipment to contact a policy server after successful authentication of an extensible authentication protocol.
 13. The system of claim 11, wherein the cellular radio access network is configured to receive, from the user equipment, an indication of availability, to the user equipment, of cellular radio access on the cellular radio access network.
 14. The system of claim 11, wherein the off-load condition comprises a cell network congestion state or a quality of service of the cellular radio access network.
 15. The system of claim 11, wherein the cellular radio access network is configured to instruct the user equipment to prioritize access to the non-cellular radio access network over the cellular radio access network.
 16. The system of claim 11, wherein the cellular radio access network is configured to instruct the user equipment to prioritize access to the cellular radio access network over the non-cellular radio access network.
 17. The system of claim 11, wherein the cellular radio access network is configured to prevent the user equipment from returning to the cellular radio access network prior to determining that the off-load condition no longer exists.
 18. The system of claim 11, wherein the cellular radio access network is configured to return a plurality of user equipment that is located within the area of the cellular radio access network to the cellular radio access network.
 19. The method of claim 11, wherein the non-cellular radio access network is a Wi-Fi network.
 20. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to: determine that an off-load condition no longer exists in an area of a cellular radio access network that a user equipment is located in; send instructions, via a non-cellular network, to the user equipment to return to the cellular radio access network. 